Skip to content

[release-4.19] OCPBUGS-56131: Retry SSH server initialization #3139

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Aug 13, 2025
Merged

[release-4.19] OCPBUGS-56131: Retry SSH server initialization #3139

merged 1 commit into from
Aug 13, 2025

Conversation

@openshift-cherrypick-robot
Copy link

@openshift-cherrypick-robot openshift-cherrypick-robot commented Aug 5, 2025

This is an automated cherry-pick of #3135

/assign sebsoto

@sebsoto
Retry SSH server initialization
0946260 
Attempts to fix an issue where Windows Server 2019 machines were not
having a running SSH server due to network instability.
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Aug 5, 2025
Merged
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 5, 2025

@openshift-cherrypick-robot: Jira Issue OCPBUGS-58282 has been cloned as Jira Issue OCPBUGS-60135. Will retitle bug to link to clone.
/retitle [release-4.19] OCPBUGS-60135: Retry SSH server initialization

In response to this:

This is an automated cherry-pick of #3135

/assign sebsoto

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot changed the title [release-4.19] OCPBUGS-58282: Retry SSH server initialization [release-4.19] OCPBUGS-60135: Retry SSH server initialization Aug 5, 2025
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 5, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 5, 2025

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-60135, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-58282 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This is an automated cherry-pick of #3135

/assign sebsoto

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

jrvaldes
jrvaldes approved these changes Aug 5, 2025
View reviewed changes
Copy link
Contributor

@jrvaldes jrvaldes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 5, 2025
@sebsoto sebsoto changed the title [release-4.19] OCPBUGS-60135: Retry SSH server initialization [release-4.19] OCPBUGS-56131: Retry SSH server initialization Aug 12, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 12, 2025

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-56131, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-56131 to depend on a bug targeting a version in 4.20.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This is an automated cherry-pick of #3135

/assign sebsoto

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@sebsoto
Copy link
Contributor

sebsoto commented Aug 12, 2025

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 12, 2025

@sebsoto: This pull request references Jira Issue OCPBUGS-56131, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-56131 to depend on a bug targeting a version in 4.20.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@mansikulkarni96
Copy link
Member

mansikulkarni96 commented Aug 12, 2025

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 12, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jrvaldes, mansikulkarni96, openshift-cherrypick-robot

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [jrvaldes,mansikulkarni96]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 12, 2025
@sebsoto sebsoto removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Aug 12, 2025
@sebsoto
Copy link
Contributor

sebsoto commented Aug 12, 2025

/retest-required

@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 12, 2025

/retest-required

Remaining retests: 0 against base HEAD a282150 and 2 for PR HEAD 0946260 in total

@jrvaldes
Copy link
Contributor

jrvaldes commented Aug 12, 2025

/override ci/prow/platform-none-vsphere-e2e-operator

@jrvaldes
Copy link
Contributor

jrvaldes commented Aug 12, 2025

platform-none-vsphere-e2e-operator test failed at mustgather, WMCO test suite passed

https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_windows-machine-config-operator/3139/pull-ci-openshift-windows-machine-config-operator-release-4.19-platform-none-vsphere-e2e-operator/1955325925662920704#1:build-log.txt%3A72

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 12, 2025

@jrvaldes: Overrode contexts on behalf of jrvaldes: ci/prow/platform-none-vsphere-e2e-operator

In response to this:

/override ci/prow/platform-none-vsphere-e2e-operator

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@sebsoto
Copy link
Contributor

sebsoto commented Aug 13, 2025

/override ci/prow/gcp-e2e-operator ci/prow/nutanix-e2e-operator

GCP passed previously, nutanix is not functioning

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 13, 2025

@sebsoto: Overrode contexts on behalf of sebsoto: ci/prow/gcp-e2e-operator, ci/prow/nutanix-e2e-operator

In response to this:

/override ci/prow/gcp-e2e-operator ci/prow/nutanix-e2e-operator

GCP passed previously, nutanix is not functioning

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 13, 2025

@openshift-cherrypick-robot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/nutanix-e2e-operator 0946260 link unknown /test nutanix-e2e-operator

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit db2e16c into openshift:release-4.19 Aug 13, 2025
18 checks passed
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 13, 2025

@openshift-cherrypick-robot: Jira Issue OCPBUGS-56131: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-56131 has been moved to the MODIFIED state.

In response to this:

This is an automated cherry-pick of #3135

/assign sebsoto

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@sebsoto
Copy link
Contributor

sebsoto commented Aug 21, 2025

/cherry-pick release-4.18

@openshift-cherrypick-robot
Copy link
Author

openshift-cherrypick-robot commented Aug 21, 2025

@sebsoto: new pull request created: #3205

In response to this:

/cherry-pick release-4.18

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Aug 21, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@mansikulkarni96 mansikulkarni96 Awaiting requested review from mansikulkarni96

@sebsoto sebsoto Awaiting requested review from sebsoto

1 more reviewer

@jrvaldes jrvaldes jrvaldes approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@sebsoto sebsoto

@jrvaldes jrvaldes

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@openshift-cherrypick-robot @openshift-ci-robot @sebsoto @mansikulkarni96 @jrvaldes